Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.

I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.

Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

What will versions of conda-build prior to 3.18.12 do with this run_export. My reading of conda/conda-build#3868 is that the weak run_export will be applied in this case.

Not a reason to hold this up, just something to keep in mind.

It might be good to ensure that conda-build >=3.18.12 is used when building noarch packages if not all packages.

@jjhelmus, I agree. I'll add a condition to conda-forge-ci-setup.

I first thought of adding a check to conda-build to error out if an unknown run_exports type is used by a package, but that's not going to work with older conda-build releases, so I didn't. If you think it'll be useful for a new type of run_exports, I can send a PR.